Problem Note 45705: Optimizer might "fail to respond" because of floating point error
When using the option "method=TRUREG" in procedures that support the nloptions statement, you might notice that optimization fails to respond. This happens because of a floating point error and overly tight convergence criteria, which causes the optimizer to think it can make progress when it actually cannot. This issue can affect any procedure that performs optimization using trust region methods.
To workaround the issue, use one of the options below:
- Change the method option of the nloptions statement.
- Loosen the FCONV or XCONV criteria from the default.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
SAS System | Base SAS | z/OS | 9.21_M3 | 9.3_M1 | 9.2 TS2M3 | 9.3 TS1M1 |
Solaris for x64 | 9.21_M3 | 9.3_M1 | 9.2 TS2M3 | 9.3 TS1M1 |
OpenVMS on HP Integrity | 9.21_M3 | 9.3_M1 | 9.2 TS2M3 | 9.3 TS1M1 |
Linux for x64 | 9.21_M3 | 9.3_M1 | 9.2 TS2M3 | 9.3 TS1M1 |
Linux | 9.21_M3 | 9.3_M1 | 9.2 TS2M3 | 9.3 TS1M1 |
HP-UX IPF | 9.21_M3 | 9.3_M1 | 9.2 TS2M3 | 9.3 TS1M1 |
64-bit Enabled Solaris | 9.21_M3 | 9.3_M1 | 9.2 TS2M3 | 9.3 TS1M1 |
64-bit Enabled HP-UX | 9.21_M3 | 9.3_M1 | 9.2 TS2M3 | 9.3 TS1M1 |
64-bit Enabled AIX | 9.21_M3 | 9.3_M1 | 9.2 TS2M3 | 9.3 TS1M1 |
Windows Vista for x64 | 9.21_M3 | 9.3_M1 | 9.2 TS2M3 | 9.3 TS1M1 |
Windows Vista | 9.21_M3 | 9.3_M1 | 9.2 TS2M3 | 9.3 TS1M1 |
Windows 7 Ultimate x64 | 9.21_M3 | 9.3_M1 | 9.2 TS2M3 | 9.3 TS1M1 |
Windows 7 Ultimate 32 bit | 9.21_M3 | 9.3_M1 | 9.2 TS2M3 | 9.3 TS1M1 |
Windows 7 Professional x64 | 9.21_M3 | 9.3_M1 | 9.2 TS2M3 | 9.3 TS1M1 |
Windows 7 Professional 32 bit | 9.21_M3 | 9.3_M1 | 9.2 TS2M3 | 9.3 TS1M1 |
Windows 7 Home Premium x64 | 9.21_M3 | 9.3_M1 | 9.2 TS2M3 | 9.3 TS1M1 |
Windows 7 Home Premium 32 bit | 9.21_M3 | 9.3_M1 | 9.2 TS2M3 | 9.3 TS1M1 |
Windows 7 Enterprise x64 | 9.21_M3 | 9.3_M1 | 9.2 TS2M3 | 9.3 TS1M1 |
Windows 7 Enterprise 32 bit | 9.21_M3 | 9.3_M1 | 9.2 TS2M3 | 9.3 TS1M1 |
Microsoft Windows XP Professional | 9.21_M3 | 9.3_M1 | 9.2 TS2M3 | 9.3 TS1M1 |
Microsoft Windows Server 2008 for x64 | 9.21_M3 | 9.3_M1 | 9.2 TS2M3 | 9.3 TS1M1 |
Microsoft Windows Server 2008 | 9.21_M3 | 9.3_M1 | 9.2 TS2M3 | 9.3 TS1M1 |
Microsoft Windows Server 2003 for x64 | 9.21_M3 | 9.3_M1 | 9.2 TS2M3 | 9.3 TS1M1 |
Microsoft Windows Server 2003 Standard Edition | 9.21_M3 | 9.3_M1 | 9.2 TS2M3 | 9.3 TS1M1 |
Microsoft Windows Server 2003 Enterprise Edition | 9.21_M3 | 9.3_M1 | 9.2 TS2M3 | 9.3 TS1M1 |
Microsoft Windows Server 2003 Datacenter Edition | 9.21_M3 | 9.3_M1 | 9.2 TS2M3 | 9.3 TS1M1 |
Microsoft® Windows® for x64 | 9.21_M3 | 9.3_M1 | 9.2 TS2M3 | 9.3 TS1M1 |
Microsoft Windows XP 64-bit Edition | 9.21_M3 | 9.3_M1 | 9.2 TS2M3 | 9.3 TS1M1 |
Microsoft Windows Server 2003 Enterprise 64-bit Edition | 9.21_M3 | 9.3_M1 | 9.2 TS2M3 | 9.3 TS1M1 |
Microsoft Windows Server 2003 Datacenter 64-bit Edition | 9.21_M3 | 9.3_M1 | 9.2 TS2M3 | 9.3 TS1M1 |
Microsoft® Windows® for 64-Bit Itanium-based Systems | 9.21_M3 | 9.3_M1 | 9.2 TS2M3 | 9.3 TS1M1 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Type: | Problem Note |
Priority: | alert |
Date Modified: | 2012-04-18 10:19:45 |
Date Created: | 2012-02-17 10:08:13 |